Identification of distinguishable anomalies extracted from real time data streams

ABSTRACT

A big data processing system includes a workload trimming function that separates out from among a set of identified anomalies, those that are clearly outliers, rather than ones residing within clusters of anomalies as mapped within an anomalies distribution space. The outlier anomalies are not subjected to a computationally-intensive anomalies aggregating process and thus, processing resources are conserved.

BACKGROUND

Voluminous amounts of data may be produced by server event loggings in an enterprise wide data processing system. This kind of data is sometimes referred to as a form of “Big Data.”

It has been proposed to extract anomaly indications in real time from real-time Big Data streams and to present the same to human administrators as alerts. However, the volume of data is generally too large to provide meaningful and actionable information for human users and it is often coded in varying manners which makes extraction of any meaningful/actionable information difficult. More specifically, a typical event data stream (e.g., Apache™ log file) may have thousands, if not hundreds of thousands of records with each record containing large numbers of numerical and categorical fields/features. Semantic names of fields can vary among data sources and thus there is little consistency. New data sources can be introduced having unknown encoding formats that human users do not have previous experience with. Formats of associated numeric and/or qualitative items inside the data streams can vary as between different data sources (e.g., logging systems of different servers). Many of the event records contain information which is not indicative of any relevant anomaly whatsoever. Among those records that do contain data indicative of an anomaly, many of such records can contain duplicative insight information with respect to the underlying fault or failure and thus they do not provide additional useful information beyond that already provided by a first of these records. Reporting each as a separate alert adds confusion and diversion rather than providing useful, actionable information. Also within each anomaly indicating record there can be many fields whose numeric and/or qualitative information is of no causal relevance with respect to an indicated one or more anomalies. Thus it is difficult to extract and provide meaningful and useful information from such voluminous amounts of real time streamed data for use in forming alerts that have practical utility (e.g., comprehend-ability and action-ability) to human users such as web administrators and/or other system administrators.

It is to be understood that this Background section is intended to provide useful introductory information for understanding here disclosed and novel technology. As such, the Background section may include ideas, concepts or recognitions that were not part of what was known or appreciated by those skilled in the pertinent art prior to corresponding invention dates of subject matter disclosed herein.

BRIEF SUMMARY

According to one aspect of the present disclosure, a Big Data mining and reports producing system is disclosed that automatically identifies which fields in the records of each of plural event streams are the fields to be focused on for extracting relevant feature information to identify nonduplicative (e.g., distinguishable) anomalies and identifying one or more prime and secondary features (e.g., meaningfully distinguishing features) that cross correlate to those anomalies.

Identification of likely to be relevant features is based on an expert knowledge database that is heuristically developed through experience by a global set of domain experts and also by local experiences of specific users. This heuristically developed experience may be stored as expert rules (e.g., IF-THEN rules) in the expert knowledge database.

Identification of likely to be duplicative, log records (duplicative in terms of identifying unique anomalies) is automatically performed by statistical clustering analysis such as Kernel Density Estimation (KDE).

Reporting of anomalous behaviors is automatically performed by an anomalies categorizing, aggregating and de-duplicating mechanism.

This Brief Summary provides a selected subset of introductory concepts in simplified form where the latter and further ones are described in greater detail in the below Detailed Description section. This Brief Summary is not intended to identify key or essential aspects of the disclosed and claimed subject matter, nor is it intended to be used as an aid in determining the scope of claimed subject matter. The scope of the disclosure is to be determined by considering the disclosure in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a schematic diagram of an enterprise wide data processing system including a plurality of servers.

FIG. 1B is a schematic diagram tying together a number of concepts including that of obtaining metric measurements from respective servers of FIG. 1A, of logging corresponding measurement sample points, of defining global and local anomalies (by way of violated normalcy rules) and of identifying prime and secondary features that correlate to and allow for distinguishing amongst the defined anomalies.

FIG. 1C is a schematic diagram for explaining a progression from fault to nascent failure (minor anomaly) to major failure (major anomaly).

FIG. 1D is a schematic diagram for explaining by analogy, the concept of distinguishing features in respective domains.

FIG. 2A is a flow chart describing one embodiment of a processor for extracting data/features from machine-generated data.

FIG. 2B is a flow chart depicting a workload trimming operation.

FIG. 2C depicts further content of the knowledge database of FIG. 2A and associated models.

FIGS. 3A-3D are two dimensional graphs depicting workload trimming for single variate anomalies.

FIGS. 4A-4C are multi-dimensional graphs depicting workload trimming for multi-variate anomalies.

FIGS. 4D is a legend.

FIGS. 5A-5B depict a method and system for identifying the more distinguishing features to be used for multi-variate anomalies and reporting of same.

FIGS. 5C is a legend.

FIG. 6 depicts a graphical user interface including an alerts management dashboard.

FIG. 7 is a schematic diagram depicting more details of an enterprise wide system such as that of FIG. 1A.

DETAILED DESCRIPTION

FIG. 1A is a schematic diagram showing a selected few representative parts of an integrated client-server/internet/cloud system 100 (or more generically, an integrated enterprise system 100) to which the here disclosed technology may be applied. Additional details respecting such systems will be provided later below in conjunction with FIG. 7.

System 100 is a machine system having distributed resources including a variety of differently-located and interconnected data processing and data communication mechanisms such as, customer-sited client units (e.g., wireless smartphone 110 at user location LocU1) and differently located enterprise servers (e.g., in-cloud servers 131, 132, . . . 13 n (not all shown) having respective siting locations LocX1, LocX2, LocXn). Each client unit (e.g., 110—only one shown but understood to be exemplary of thousands of such clients) is configured to transmit requests for various services to one or more of in-cloud and/or in-internet enterprise servers such as servers 131, 132 . . . 13 n (not all shown). It is to be understood that the client and server units each typically includes a CPU and/or other digital data processing circuitry, memory embedded within and/or ancillary to the data processing circuitry, communication circuitry configured to enable various kinds of data transference including by wired and wireless means and computer code physically encoded in one or more forms of memory including instruction codes configured for causing one or more of the data processing circuits to perform called-for application servicing or system servicing operations. The instruction codings may vary from one client machine (e.g., 110) to the next (not shown) for example because they have different operating systems (e.g., Apple iOS™ versus Google Android™) and/or different background programs for producing background event reporting streams (e.g., events such switch from WiFi to cellular communication mode due to lost WiFi signal).

For purpose of customer satisfaction, it is often desirable to provide short response times (if not substantially instant ones) for respective client service requests. Also system bandwidth should be large enough to simultaneously service large numbers of demanding requests from large numbers of clients. Sometimes various portions of the system encounter faults or failures that prevent them from adequately servicing customer demand loads and/or system servicing demand loads. In light of this, enterprise resource monitoring, managing and/or debugging means are typically provided at various server occupied locations (e.g., LocX3 of FIG. 1A) and these means are tasked with, among other jobs, the job of monitoring mission-vital points within the system 100 and generating corresponding event reporting data streams (e.g., in the form of event logs like 141, 142, 143). The event logs provide voluminous amounts of measurement data about the behaviors of the monitored servers. Not all event logs are the same. One (e.g., 141) may be coded in accordance with a first operating system (OS1) and may store records related to web based operations. Another (e.g., 142) may be coded in accordance with a different second operating system (OS2) and may store records related to internal performance aspects of local servers, such as CPU utilization percentage, memory usage efficiencies and so on.

Aside from its inclusion of the end-user devices (e.g., 110) and the in-cloud and/or in-Internet servers (e.g., 131, 132, . . . , 13 n) the system 100 typically comprises: one or more wired and/or wireless communication fabrics 115 (only one shown in the form of a wireless bidirectional interconnect) that couples the end-user client(s) 110 to further networked servers 120 (not explicitly shown, and can be part of an Intranet or the Internet) where the latter may operatively couple by way of further wired and/or wireless communication fabrics 125 (not explicitly shown) to further networked servers 130 such as 131, 132, . . . , 13 n). Although not shown the communication fabrics (e.g., 115, 125) may each have their own event data stream generators.

Still referring to FIG. 1A, item 111 of client 110 represents a first user-activateable software application (first mobile app) that may be launched from within the exemplary mobile client 110 (e.g., a smartphone, but could instead be a tablet, a laptop, a wearable computing device; i.e. smartwatch or other). Item 112 represents a second such user-activateable software application (second mobile app) and generally there are many more. Each end-user installed application (e.g., 111, 112, etc.) can operate in a different usage domain and can come in the form of nontransiently recorded digital code (i.e. object code or source code) that is defined and stored in a memory for instructing a target class of data processing units to perform in accordance with end-user-side defined application programs (‘mobile apps’ for short) as well as to cooperate with Internet/Cloud side applications implemented on the other side of communications links 115 and/or 125. Each app (e.g., 111, 112) may come from a different business or other enterprise each having its own unique business needs and goals (e.g., one sells hard covered books while another provides grocery deliveries and yet another real time online software services). Generally, each enterprise is responsible for maintaining in good operating order its portions of the system (e.g., Internet, Intranet and/or cloud computing resources). However, for efficiency sake they may delegate many of the monitoring and maintaining tasks to a centralized SAAS provider (not shown, a Software As A Service entity). The SAAS provider may use experience with its many enterprise customers to glean knowledge about normal system behavior on a global level (e.g., as applicable to the Internet as whole) and also about normal system behavior for specific ones or classes of its enterprise customers (localized knowledge).

Referring next to FIG. 1B, approaches for the detection and classification of anomalous system behavior will now be described by means of an integrated set 150 of three interrelated graphs 155, 160 and 170. Anomalous behavior can be intermittent rather than constant. In other words it is not guaranteed to always occur at any specific moment of time while a respective portion of the system is being monitored. Thus the system has to be monitored over long periods of time (e.g., 24 Hrs./7 Days) and with short sampling durations (e.g., one status record every few milliseconds) so that voluminous amounts of data are captured and recorded for large numbers of monitored locations at which short-lived faults or failures may occur. The monitored locations may include ones relating to hardware operations, software operations, firmware operations and/or data communication operations (wired or wireless).

By way of an example of how various failures may arise, consider a system in which a large number of execution threads (XT1, XT2, XT3, . . . , XTm, . . . , XTn) are launched within a corresponding one or more data processing units (e.g., CPU's). Any given one or more execution threads (e.g., XT2 inside graph 160) may by chance miss encounters with, or have multiple encounters with fault regions and/or a cascade of their consequential failure regions (e.g., fault and failure illustrated as a combined FF2 region) where these regions populate a one or multi-dimensional faults and failures mapping space (e.g., one having plural operational feature dimensions such as 165 and 167).

Briefly, and with reference to FIG. 1C; fault and failure need not be coincidental things. In a first state 181, a nail may lie in wait along a roadway traveled by many cars until one unlucky car runs its tire over the nail at a first time point and first location (where the lying in wait nail is a fault condition that the unlucky car collides with). This creates a first and relatively small failure condition in the tire (e.g., a small air leak, state 182 farther down the road at a second location as the nail starts to dig in) and then, as events progress, the nail digs in yet deeper until there is a tire blowout (catastrophic failure, state 183) at a third time point and third location. Depending on where and how the car with blown-out tire ends up (e.g., upright on road shoulder or upside down and still in roadway as depicted by 183) it may represent a new fault state into which other cars may collide, thus providing a growing cascade of faults, failures and consequential new faults and failures. With respect to the top left plot 160 in FIG. 1B and for sake of simplicity, fault and failure in the described machine system will be considered here as if they occur at a substantially same time and same location and the possibility for a growing cascade of faults, failures and consequential new faults and failures will be understood to be present even though not explicitly depicted in plot 160 in FIG. 1B.

A general goal of system administrators is to identify and repair faults and failures as soon as possible (preferably in real time) before minor failures grow into larger or catastrophic and cascading failures. However, even when relatively minor failures occur or more major and even worse, catastrophic failures occur, it is a problem for system administrators to first spot those failures in a meaningful way, comprehend what the consequences might be (so as to prioritize between competing alerts), identify the respective locations of fault and failure, identify their casually related fault states (e.g., corresponding to state 181 of FIG. 1C, where the nail in the road might be deemed the fault that needs to be repaired/ removed) and take immediately corrective action where practical. However, the reporting of faults and failures as meaningful alerts to system administrators is not a trivial matter.

It is to be noted that while one of the illustrated operation executing threads (e.g., XT2 inside graph 160 of FIG. 1B) may be lucky and miss encounters with fault regions (e.g., analogizable to nails on the road, but where the car of FIG. 1C luckily does not run into any), other executing threads such as the illustrated first thread XT1 may not be so lucky and may meander through the illustrated fault/failure space 160 so as to collide with multiple ones of fault and/or failure occurrence regions such as illustrated at 161 (FF1) and at 163 (FF3) at respective fault collision time points t1 and t3. In the same environment where the first operation executing thread (XT1) collides with fault/failure regions 161 (FF1) and 163 (FF3), there can be many other and similarly situated execution threads (XTm,. . . , XTn) optionally launched at different times which also collide with the same fault/failure regions (e.g., 161, 163) so as to result in the generating of substantially similar event records indicative of substantially same encounters but at respective time points, Tm, . . . , Tn. (Also it is to be observed with respect to the multiply-collided into fault/failure region 163 (FF3) that it may produce a growing cascade of further faults, failures and consequential new faults and failures much as an overturned car (e.g., 183 of FIG. 1C) can if it lands in the middle of a heavily used roadway on a stormy dark night. For sake of simplicity, this further possibility is not depicted in plot 160.)

For the latter set of cases (e.g., collisions by XT1, XTm-XTn), if the behaviors of the unlucky execution threads (e.g., XT1, XTm-XTn) are appropriately monitored for, and the consequences of their corresponding collisions with one or more of the illustrated FF occurrence regions 161 and 163 (at respective time points t1 and t3 and Tm-Tn) are captured in recorded log data of corresponding timeslots (similar to timeslots T1 and T3 of graph 155) covering those specific time points, then later (but still in a substantially real time context); it might be possible to infer from the captured log data of those timeslots (e.g., T1 and T3) where, when and how the faults and/or failures occurred based on strong correlation to certain dimensionality axes of a fault/failure space (e.g., F/F space 160). Certain dimensionality axes of this F/F space 160 will be referred to herein as “highly meaningful and distinguishing features” while others as less meaningful/distinguishing and yet others as non-meaningful and/or non-distinguishing ones. An explanation of what these dimensionality axes are and why some dimensionality axes may be deemed “highly meaningful/distinguishing” ones (and are thus named, highly meaningful/distinguishing features) and others may be deemed as non-distinguishing ones or less meaningful/distinguishing ones is presented soon below in conjunction with FIG. 1D.

First it is to be noted that the so-called, consequences of corresponding collisions with faults (e.g., state 181 of FIG. 1C) can appear in the form of minor anomalies (minor deviations from normal behavior—such as state 182 of FIG. 1C, where the air leak might be barely detectable), medium anomalies meaning ones with greater such deviations from normal behavior or major and perhaps catastrophic failures (e.g., where the corresponding behavior of an initiated operation (e.g., XT1) does not complete—for example no response is generated to a service request as opposed to a late response; the latter catastrophic outcome being exemplified by analogy in state 183 of FIG. 1C). Accordingly, if anomalous behaviors are timely reported in a meaningful way (e.g., reported in substantially real time whereby administrators may have opportunity to take meaningful action and avert worse consequences), it might be possible to then repair the faults or avoid further encounters with the faults (FF locations in F/F space 160) or reduce the frequency of such encounters and/or the consequences of such encounters with the discovered fault regions. The detection and classification of anomalous behavior within a machine system (e.g., 100 of FIG. 1A) will be described shortly with reference to a second plot 155 of FIG. 1B.

Discussion thus far with respect to the first graph 160 of FIG. 1B might lead readers to incorrectly assume that one is able to see in practice a graph such as 160 and to see real time executing threads meandering their way through a fault/failure space (160) and colliding with observable fault phenomenon. However, in reality, there is no currently known device for definitively displaying a graph such as 160 and capturing all meanderings and all collisions. The identities of the dimensional axes (e.g., 165 horizontally and 167 vertically, also referred to herein as “features”) for optimal analysis are typically unknown and the useful dimensionality number (e.g., 2D, 3D, 4D, . . . , meaning the numbers of such axes—be they orthogonal or not) of the space are also typically unknown. That is why FIG. 1B identifies graph 160 as a “hidden” fault/failure space.

Despite the “hidden” nature of the F/F space 160 it has been found that heuristically acquired knowledge can be used to make intelligent guesses at some likely identities for relevant ones of the dimensional axes (e.g., feature plotting axes 165, 167) of space 160 based on application domain and context. For example, experience indicates that the illustrated X axis (165) should, in general not be a timeline when the domain is that of, for example, timely responding to web page serve up requests. One reason is because plural execution threads such as XTm through XTn may be launched at very different times and their corresponding collision times Tm through Tn with a same fault and/or failure region FF3 (163) will then spread far apart out along a time-line X axis rather than showing the collisions (and/or consequential anomalous behaviors—a.k.a. failures) as being collectively concentrated (clustered) over one point or concentrated zone (e.g., 165 a) of the illustrated horizontal axis 165.

More specifically and based on experience with certain kinds of application domains (e.g., requestor initiated failures), it has been found that horizontal axis 165 is more usefully structured as a series of IP address sampling points distributed along horizontal axis 165 and identifying where anomalous service requests are coming from in terms of IP address. (Another example for identifying where anomalous service requests are coming from might utilize an X axis populated by geographic location designators such as postal zip codes.) This kind of more usefully populated plotting-along axis is referred to herein as a prime meaningful/distinguishing feature axis for reasons that will become apparent below. Identities of meaningful/distinguishing feature axes (prime or secondary); as opposed to those which are not distinguishing or meaningful, may be deduced from information collected in knowledge collecting databases and from various kinds of information found within the captured data logs (e.g., 141-143 of FIG. 1A).

By way of a nonlimiting example of how and why some dimensionality axes may be useful and others not so much, assume that fault/failure region 163 (also identified as FF3 in plot 160) strongly correlates with one or a concentrated plurality (165 a) of Internet Protocol addresses (IP addresses) distributed along a source IP Addr axis line 165 due to certain web hacking activities originating from zombie computers having those IP addresses. (The term ‘zombie computer’ is attributed here to computers of unsuspecting innocent users where through viral infection, background tasks of the computers have been taken over by a malicious hacker.) The zombie computers having the correlating one or more IP addresses (165 a) may be responsible for a large number of execution threads (e.g., XTm, . . . , XTn) all intersecting with a same fault or failure modality (e.g., Denial Of Service (DOS) and excessive response times imposed on others) at location 163 of the hidden fault/failure space 160. The same exemplary failure region 163 may additionally correlate with a certain HTTP web service request code or sequence of codes (167 a) found along a secondary features line 167 that has different request codes (or sequences of such) distributed along its length. A reason might be that all of the zombie computers (the ones taken over by the malicious hacker) are issuing that same HTTP request code or code sequence (167 a) to launch their DOS (denial of service) attacks. By discovering that fault/failure region 163 clusters about zone 165 a of the horizontal axis (e.g., a collection of specific IP addresses) and/or about zone 167 a of the vertical axis (e.g., a collection of specific HTTP request codes), system administrators can begin to uncover the underlying causes. In other words, there is a meaningful cause-and consequence relationship between certain IP addresses, certain HTTP request codes, temporally later slow response times and the anomalies of certain transaction records. It is to be understood that although the graph shown at 160 is a two dimensional (2D) one, it is to be appreciated that placement of fault and/or failure regions (e.g., 161, 162, 163) may be within spaces having a greater number of dimensions (e.g., 3D, 4D etc.) or within a one dimensional space (1D). FIG. 4A (discussed below) shows an example of mapping anomalies (475, 476) in a multi-dimensional fashion.

Referring next to FIG. 1D, an analogy is used to explain what is meant by a meaningfully distinguishing feature axis and why some dimensionality axes of an anomalies displaying space (e.g., 160) can be deemed highly meaningful/distinguishing ones, some can be deemed as less distinguishing ones and yet others as non-distinguishing or meaningful ones. In the hypothetical example 190 of FIG. 1D, a first-person 191 is to be compared against second and third persons 195 and 196 for the purpose of determining whether they are substantially twins or significantly different from one another (e.g., for the contextual purpose of taking blood from a first to safely transfuse into the other). This attempt of trying to match persons corresponds to comparing a first anomaly (e.g., 151 of the graph 155) with one or more further anomalies (e.g., 153 of FIG. 1B) for the purpose of determining whether they provide substantially same meaningful information (and thus cluster within a meaningfully distinguishing anomaly space) or whether at least one is significantly different from the others (and thus is spaced far apart within anomaly space). Although FIG. 1C shows a comparing of, and clustering together of just two persons, 191 and 195 based on commonality of highly distinguishing and meaningful features, it is to be understood that the example can be extrapolated to a comparing of, and clustering together of a large pool of people (e.g., 10's or hundreds of such persons) based on commonality of a predetermined set of meaningful/distinguishing features (for a predetermined purpose/context; e.g., blood transfusion) while selectively excluding from the pool one or a small number of persons (e.g., person 196) who for one or more reasons, clearly does not belong.

Due to a lifetime of experience, most humans find it intuitively obvious as to which “features” (e.g., among observable possibilities 191 a-191 s plus others, e.g., 193 a, 193 b, 194) to focus upon when determining whether two persons (e.g., 191 and 195) are basically twins (and thus belong to a common pool of substantially alike people) or whether one of them (e.g., 196) is significantly different from one or more of the others (and thus does not belong to the common pool of substantially alike people). Some key distinguishing features that would likely be examined based on lifetime collection of experience may include: vertical body height (as measured from the heel to top of head), horizontal shoulder width (e.g., 193 b), weight (194) eye color and a compounding of natural hair color and hair texture (e.g., curly versus straight and blonde versus brunette or redhead). Yet other keyed-on features might include facial ones such as nose size and shape, ear size and shape and chin structure and shape. From these it might be quickly deduced that the second illustrated person 195 is substantially a twin of the first 191 while the third illustrated person 196 is an odd one who clearly does not belong in the same pool as do first and second persons 191 and 195. Among the utilized features for distinguishing persons who are clearly non-matching, there may be ones that are lower cost and/or faster distinguishing ones. For example, in looking for a likely twin of first person 191 among a large pool (e.g., hundreds) of distal other persons, it may be quicker and of lower cost to first measure and distribute the others according to height rather than eye color because height measurement does not require close up inspection whereas eye color usually does and therefore, it may be faster and cheaper to first eliminate based on height before testing for eye color. This being merely an example.

Also importantly, and again due to a lifetime of experience, most humans would understand which features to not focus upon when trying to determine how different or the same one person is from the next. In other words, they would have some notions of which features in a potentially infinitely dimensioned features space to immediately exclude. For example, one would normally not concentrate on the feature of how many fingers (191 s) are present on each hand or how many toes (191 n) on each foot of the to be compared persons. Those would be examples of generally non-distinguishing non-meaningful features that are understood to be so based on a knowledge base of rules collected over a person's lifetime. Yet other examples of non-distinguishing non-meaningful features may include taking counts of how many ears are on each head as well as how many eyes and mouths are present on each head. Examples of highly distinguishing and meaningful features might include fingerprint patterns, iris characteristic patterns and DNA analysis where the practicality (e.g., in terms of cost, speed and availability of useful measurements) of testing for the more highly distinguishing features may vary from domain to domain and/or different contexts within each domain. For example, it would not generally be practical to scan for fingerprint patterns while test subjects are in a ski slope domain 192 c and under the context of having their mittens on to prevent frostbite.

Stated otherwise, feature extraction and comparison might differ depending on the environmental domains in which the to-be-compared objects are found and the practicality of performing different kinds of comparison tests might vary based on context, even if in the same domain. A first example by analogy of different possible domains is shown at 192 a as being a hospital examination room domain where the subjects are covered by hospital gowns but can be easily examined from head to toe by a doctor or nurse (and the context of the situation may be that various invasive medical tests can be performed as a matter of practicality). A second example of possible domain is indicated at 192 b as being a business conference room/ office domain where persons are wearing formal business attire. In that case,—and assuming that for reasons of practicality other tests cannot be then performed—comparing the white shirt of a first suited businessman against the white shirt of a second businessman is not likely to provide useful distinction. So shirt color would not be a reliable distinguishing feature. On the other hand, comparing the compound description of tie color and tie pattern might provide useful distinction. Accordingly, a comparison space having shirt color as one of its dimensional axes will often fail to distinguish between different businessmen when in the office domain (e.g., seated about a conference table and each covering his face due to examining a financial report). By contrast, a comparison space having a dimensional axis of compound tie color and tie pattern will likely have a better success rate at distinguishing between different businessmen in the formal attire business domain. Of course, it will still be highly useful to distinguish based on facial features such as nose size and shape, ears, hair, etc. if one could do so quickly and at low cost in the given context.

A third exemplary domain indicates at 192 c that distinction based on facial features might not always be possible. For example if the to-be-compared persons are on a ski slope, with a bright sun behind, all fully suited up in same colored ski jackets with same hoods, same facemasks and shaded goggles then many of the conventional feature extraction approaches (e.g., eye color) will be unusable. (Of course there will still be further features such as body height, girth, weight and voice pattern that can be used.)

In light of the above, it is to be observed that domain (e.g., 192 a, 192 b, 192 c) and context (e.g., casual versus formal wear) can be an influence not only on what features are usable for meaningfully distinguishing between things (e.g., anomalous things) found in that domain but also on what might be deemed normal versus anomalous behavior in each respective domain and its contexts. For example, in a hospital ward (domain 192 a) it may be deemed normal to see patients walking around garbed only in hospital gowns. However, in a business office domain (192 b) or when on a ski slope (192 c) it may be deemed highly abnormal (anomalous) to detect persons garbed only in hospital gowns. Thus determination of appropriate domain and context can be an important part of determining what is an anomaly or not, in determining which anomalies are basically twins of one another (e.g., 191 and 195), which one or more anomalies (e.g., 196) is/are not twinned with others and in determining which of the features that are practically observable in the given domain can function as highly meaningful/distinguishing and practically measurable features for a given category of anomalies and which to a lesser degree or not at all.

In the case where an automated machine subsystem is trying to identify useful features for meaningfully distinguishing as between anomalies (e.g., failures) and faults in a fault/failure space, the answers are far less intuitive than those retrieved when distinguishing among people. This especially true when there is no previous experience with a newly introduced events data streaming system (e.g., logging system) because that may constitute a novel domain not encountered before and for which there is no experiential knowledge base. Even for domains that have been previously encountered, the mere defining of anomalies is itself problematic.

Referring to bottom left plot 155 of FIG. 1B, this plot indicates that measurements (or observations) of a measurable (or observable) parameter are taken over time and relative to a parameter measuring or otherwise distinguishing axis 157 (the Mp axis)—where in one example, the Mp parameter indicates number of service requests or number of requests per unit time. Other examples of measurable parameters include: resource utilization percentages, ratios and/or absolute values (e.g., CPU utilization as a percentage of 100% capacity, current CPU utilization over “normal” CPU utilization and CPU utilization in terms of executed instructions per unit time or floating point operations per unit time); incoming number of Web-based requests per unit time (e.g., HTTP coded requests per second); response time and/or code for each received request (e.g., HTTP coded response and time to produce in milliseconds); IP addresses of origins of received requests; number of requests per unit time from each IP address; number of requests per unit time from each geographic area (e.g., per zip code) and averages of these over longer units of time.

The vertical Mp axis 157 need not be linear or have numerical marker points (shown in 157) arranged in numerical order. It can be divided into qualitative zones (e.g., 157 a) having qualitative descriptors (e.g., similar to combination of tie color and tie pattern; red stripes on yellow background for example) instead of according to numerical markers. Examples of qualitative descriptors in the domain of web-based service requests can include: transmission quality excellent; transmission quality acceptable and transmission quality poor.

The measurement/observations-taking plotting-along axis 158 can be in units of measured time for example as time slots of one millisecond (1 ms) duration each where each such timeslot (e.g., T3) can span over one or more measurement points (e.g., the illustrated measurement sample points Mspt's). However, the measurement plot-along axis 158 can have alternative units of cross measurement Xm's other than time, for example, a linear organization of IP addresses or of a selected (masked) subportion of the request originating IP addresses or geographic locaters (e.g., postal zip codes).

Definitions for what is “normal” (NORM) and what constitutes an anomalous deviation from normal can vary from domain to domain and as between different categories of anomalies. In one embodiment, at least one of an end-user and of a reporting-system provider provides definitional rules for what constitutes “normal” (NORM) under extant conditions and what constitutes an anomalous deviation from normal. For example, one or both of minimum and maximum values (Mp(min), Mp(max)) may be defined as absolutely valued but variable positions on a parameter measuring scale 159. The measuring scale 159 may be linear, logarithmic, in numerical ascending or descending order, organized as a set of numerical values that are not necessarily in numerical order or organized as zones of qualitative descriptors (e.g., red stripes on yellow field versus blue dots on pink background field). In an alternate embodiment, at least one of the minimum and maximum values (Mp(min), Mp(max)) may be defined in relative terms based on the defined “normal” (NORM); for example as a percentage of deviation from the defined NORM value. The NORM value itself may vary with time, location and/or with changes in other parameters.

An anomaly is defined by a measurement (direct or derived) that is detected to be outside the defined normal range or ranges, for example above a defined maximum value Mp(max) or below a defined minimum value Mp(min). FIG. 1B uses five-point stars such as depicted at 151, 153 and 154 of plot 155 to identify detections of respective anomalies. When two or more anomalies (e.g., 151 and 153) are spotted as being relatively close to one another with respect to a plotting along axis (Xm 158), then a question arises as to whether these plural anomalies belong to a cluster of twin anomalies. In other words, do they represent a corresponding plurality of collisions by one or more machine operations with a same fault condition (for example FF3 of plot 160) or is the plotted closeness of these anomalies (e.g., 151, 153) merely a coincidence due to choice of the plotting along axis (Xm 158) and its depicted begin and end terminals?

Detectable anomalies are also represented as 5-point stars for example at 175 a,b,c,d,e within plot 170 of FIG. 1B. In this example, the anomalies are categorized according to types with exemplary categories including, but not being limited to: excessively long response times (171 a), excessively low CPU utilization rates (171 b), excessively low network bandwidth utilization percentages (171 c) and an otherwise specified violation of a rule for what constitutes normal (171 x) relative to a corresponding feature dimension. Here, in plot 170 the categorized anomalies (e.g., 175 a-c and 175 d-e) are plotted relative to potentially relevant or irrelevant cross axes (Xm's) where examples of such possible, plotting-along cross axes include a timeline 172, a place/location designator line 173 and a further designator line 174 that is labeled as “other”, meaning something other than time or place of request origin. Each detected or detectable anomaly (e.g., 175 a, 175 b) may be associated with its own respective place (e.g., p1, p2) where that place may indicate, for example, an IP address from which a corresponding request issued or a geographic location of a request making client machine. In other words, although the top two anomaly stars 175 a, 175 b representing long response times for timeslot tl occurred at substantially the same time, they can nonetheless respectively belong to different originating IP addresses (e.g., p1, p2). In the illustrated example they also respectively belong to different, “other” features o1 and o2. Time (172) may not be the best way of distinguishing between anomalies 175 a, 175 b. Instead other features such as places p1, p2 and “others” o1, o2 may be better suited for discerning a useful distinction between or commonality associated with exemplary anomalies 175 a, 175 b.

Consider for a moment an alternate outcome (not shown within plot 170) where the data samples for both of anomalies 175 a and 175 b were collected in the same timeslot T1 and the corresponding event log entries (177) for each of anomalies 175 a and 175 b indicates a same IP address of origin (e.g., p1) and a same “other” feature attribute (e.g., o1, where in one example o1 indicates that a same HTTP request code was provided from the same IP address of origin and was consequentially followed by each of anomalous behaviors 175 a and 175 b). In the case of this alternate outcome it may be appropriate to conclude that anomalous behaviors 175 a and 175 b are basically twins (much as persons 191 and 195 of FIG. 1D may be considered to substantially be twins) and thus the occurrence of the second anomaly 175 b may be aggregated with that of the first anomaly 175 a and a single alert may be reported for both instead of issuing plural separate alerts for what are substantially same anomalies. This aggregation of detection of plural anomalies for forming a corresponding single alert (transforming many anomalies into a single alert) is referred to herein as aggregation of anomalies. More specifically, and with brief reference to FIG. 6, items 645 a, 645 b, . . . , 645 n may be a collection of tens, hundreds or thousand of log records each containing as indication of one or more anomalous behaviors. However, this large pool of log records has been converted into a single alert report 610 that succinctly proposes a diagnosis (e.g., 630) based on analysis of a ranked set 612 of distinguishing features (e.g., 612 a, 612 b, etc.). The large set of anomaly indicating log records have been aggregated to form a single alert report.

Consider next, however, the case illustrated in plot 170 where anomalous behaviors 175 a and 175 b were captured as measurement samples obtained by coincidence in a same timeslot (e.g., T1) but nonetheless the first anomaly 175 a is recorded as having origin place pl and other feature of while the second anomaly 175 b is recorded as having different origin place p2 and different other feature o2. In that case (the illustrated case) it may be appropriate to treat the first and second anomalous behaviors 175 a and 175 b as significantly different anomalies and to not aggregate them together for forming a same alert (e.g., 610 of FIG. 6). It may be useful in that case to designate the measurements-capturing timeline slots (of horizontal axis 172) as not providing useful information for distinguishing between the significantly different anomalies 175 a and 175 b because 175 a and 175 b appeared in a same timeslot T1 and yet they are significantly different. In other words, in this first exemplary case the dimensional axis of time (172) is found to be a non-distinguishing feature with respect to significantly different anomalies 175 a and 175 b. This might be analogous to the realization in the case of FIG. 1D that, just because patients 191 and 196 arrived at the emergency room on the same night (e.g., same timeslot), that information is insufficient to conclude that persons 191 and 196 are twins.

However, as a counter point, consider a second case where there is a common root fault or failure responsible for patients 191 and 196 arriving at the emergency room (or at two different hospitals) in substantially the same timeslot—for example because they were involved in a same automobile accident. In that case the timeline is a significant feature axis for the occurrence and geographic location of the emergency room is less so. In this second case it would be better to aggregate into one alert the occurrence of these chronologically interrelated events and perhaps use the time axis for locating yet other emergency room arrivals that link to the common fault or failure. In other words, the underlying fault/failure model can play an important role in determining which one or more features should be focused on which others less so. Thus there is an important connection between the fault/failure space of plot 160 and the choices made in plot 170 as to which of the many possible feature axes (e.g., 172, 173, 174, etc.) should be considered as associated relevant ones and which should be considered as unassociated irrelevant ones.

In a case where it is determined that the first and second anomalous behaviors 175 a and 175 b of plot 170 of FIG. 1B are significantly different anomalies, it may be appropriate to conclude that the correspondingly different placement attributes, p1 and p2, of the place axis 173 may be used to distinguish as between the unrelated anomalies 175 a and 175 b and therefore, the place of origin feature line 173 is a distinguishing feature (also referred to herein as a distinguishing dimension) whereas the timeline 172 in this particular instance is not a distinguishing dimension but rather merely a coincidence.

Yet additionally, it may be appropriate to conclude in the instant example that the also different other attributes, of and o2, of the other feature dimension 174 may be used to distinguish as between anomalies 175 a and 175 b and therefore, the “other” feature axis 174 is a distinguishing feature. Moreover, it may be appropriate to conclude that the combination of feature dimensions 173 and 174 may be used to better distinguish as between the different first and second anomalies 175 a and 175 b. This aggregation of plural features or dimensions of an anomaly space (e.g., 160 of FIG. 1B) so as to form a compound classifier for each of the different anomalies is referred to herein as aggregation of relevant features.

Still referring to FIG. 1B, but this time to the portion below plot 170, it is to be appreciated that the detection of significantly different anomalies and/or the detection of substantially same and thus aggregable anomalies and the subsequent generation of 1-for-1 alerts or one alert (e.g., 610 of FIG. 6) for many aggregated anomalies occurs towards an end portion 176 b of a process 176 (depicted in FIG. 1B) whose beginning portion 176 a includes a recording of event log entries 177 into a respective one or more databases. Process 176 may include an insights supplementing step 176 c in which intelligent diagnostic and/or repair/treatment recommendations are added to generated alert reports 178 based on rules stored in an expert rules knowledge database (e.g., 250 of FIG. 2A). The recorded event log entries may be stored in the form of database records (e.g., 177 a) each having a database record identifier (Record ID) and one or more database record fields, for example in the form of key-name and key-value pairs. Although just one example is illustrated of a paired keyname and keyvalue at 177 a, it is understood that each identified database record can and normally does contain a large number of fields having keyvalues for corresponding, database-named keynames, where the locations of the fields may be fixed in accordance with a keynames template or the fields may float and each may contain a respective pair of keyname and one or more associated keyvalues. In the illustrated example, the keyname is denoted as IPaddr and is understood to indicate that its corresponding keyvalue is an Internet protocol address. Not all portions of each corresponding keyvalue needs to be used for plotting out either the horizontal or vertical axes (or other dimensionality axes) of a multi-dimensional anomaly detecting plot such as illustrated at 155 in FIG. 1B. For example a predefined submask of the IPaddr keyvalue may be used rather than the whole thing. Similarly for a database record time stamping field (not shown) whose keyvalue (not shown) provides many details including day of the week (e.g., Monday), month and year; it may be sufficient to pick out only a small portion (e.g., a tokenized portion) of the information in the time stamping field such as hour, minutes and seconds while discarding the rest.

Because different databases may use different database-assigned names for their keynames, a translation may be needed for mapping from database-assigned names to common feature names used by an anomaly detection and reporting system in accordance with the present disclosure. Similarly, a further translation may be needed for mapping from database-used formats to common feature value formats used by an anomaly detection and reporting system in accordance with the present disclosure.

Referring to the flow chart of FIG. 2A, a process 200 is described for converting a large number of log file records into a substantially smaller number of anomaly detections and yet a smaller number of corresponding alerts. By way of nonlimiting example, a log file may contain thousands of event reporting records. On the other hand, only a fraction of these; say hundreds instead of thousands, may be indicative of noteworthy anomalies. Among the noteworthy anomalies, two or more may provide duplicative information whereby reporting each as a separate alert complicates an alert report rather than simplifying it.

Within the steps of process 200 there is a step 270 in which potentially duplicative anomalies are aggregated together to thereby produce one alert report in place of many detected anomalies. However, the aggregation process can be computationally intensive. For example, the aggregation process may utilize complex, expert knowledge base rules in the form of IF E1 THEN E2 ELSE E3 executable statements where E1, E2 and E3 are conditional or executional expressions. Because rules and corresponding executions can vary from domain to domain, from context to context and for different kinds of anomalies, the conditional and executional expressions may be very complex. Therefore, the more anomalies there are to consider for potential aggregation under the expert knowledge base rules, the longer it may take for the aggregation process to complete. Also, more system resources are consumed by aggregation of larger numbers of anomalies. In accordance with one aspect of the present disclosure, an aggregation bypass step is included within step 270 (see also steps 274, 276 c of FIG. 2B) so as to reduce the computation time and reduce consumption of system resources.

Process 200 may be entered into at 205. In step 210, a type of logging file (L) and a server (S) that produces that type (e.g., Apache™ logs) are picked. This picking of log file type (L) and server (S) may be considered as part of a selecting of a domain in which anomalies are to be detected and reported. Picking a different server and/or a different log file type may constitute selection of a different domain. More specifically, while Apache™ logs are directed to Internet-based page serve up activities, other types of logs may be directed to other domains of enterprise activity such as quality of wireless communications or performance and reliability of data processing resources (e.g., disk capacity, read/write rates, fragmentation, etc.).

After type and server are selected in step 210, the latest such log files of type L are obtained from server S. Next, a determination is made as to what functions are performed by different locations (e.g., different fields) within each log record of the obtained log files. In one embodiment, a pre-populated knowledge database 250 is consulted. The database 250 may include a section 251 directed to type L log files and may provide predetermined mapping rules for extracting desired feature parameters from the various fields of the log file records. More specifically, if the relevant part of a timestamp field is desired, the mapping rules may indicate that only bits 8 through 24 of a field number 7 in the record should be extracted. The mapping rules may provide for numerical transformation of the extracted bits, for example converting a 12 hour A.M./P.M. expression into a 24 hour military time expression. Similarly, for certain domains it may be desirable to use predetermined sub masks of IP addresses rather than their entireties. An example is shown in section 251 where only the most significant bits 12 through 16 are extracted from a field number 5. The mapping rules may provide for numerical transformation of the extracted bits, for example through use of an address converting look up table (LUT, not shown).

Not all of the fields in the respective records of an obtained log file necessarily include information relevant to the anomalies that are to be detected and reported about. For example, the modification or access histories for the given database record may be irrelevant to detecting and reporting of anomalous behavior within the focused upon domain. Step 210 accordingly indicates that only the domain relevant feature values will be extracted.

As mentioned above, the definition of what constitutes anomalous behavior can vary from domain to domain, from location to location and as between different contexts. Accordingly, in step 220, domain appropriate and context appropriate rules are referenced for identifying which log records contain data that is violated of normalcy rules either at a global endeavor level (e.g., an Internet servicing endeavor) or at a more localized level (e.g., selling books and other items through an Internet implemented electronics store). An example by analogy as to possible differences between global and local rules may be taken from the ski slope domain 192 b of FIG. 1D. A global rule applicable to a majority of ski slopes might be that it is anomalous behavior to ski without ski poles. However, within a minority of the ski slopes (e.g., those having ski jumps) it might be perfectly normal to ski without ski poles. Therefore the global and local rules for what constitutes normalcy may vary from place to place. Section 252 of the illustrated knowledge database may include a global violation rule applicable to general Internet-based page productions where the acceptable response time for a page request is between 5 and 10 seconds. On the other hand, for an identified specific Internet-based endeavor, the corresponding local violation rule may have a different range such as between 6 to 8 seconds. Therefore, depending on whether global or local rules are used different ones of scanned log records may be deemed to contain anomalies or to instead be indicative of normal behavior.

As indicated above, not all feature dimensions are worthwhile for testing for anomalous data. Some feature dimensions are simply unlikely to provide any information of interest. An example in the hospital domain 192 a of FIG. 1D was the feature domain indicating how many fingers are found on the hands of each patient. A comparable example in the domain of server computers (of a predetermined model line) might be the feature domain indicating how many CPUs are found in each server. In view of this, the normalcy violating tests of step 220 are preferably limited to predetermined ones of feature dimensions that are deemed by the knowledge database to be the more distinguishing features for the given domain and context. The illustrated section 253 of the knowledge database is shown to include a list identifying the most distinguishing single-variate features of the given domain. Although not shown, the knowledge database may further include lists identifying less distinguishing single-variate features and listing single variate features that are non-distinguishing for the given domain and/or context. Thus, this feature is categorizing portion (253) of the knowledge database 250 may be consulted when performing step 220 and identifying the records whose fields contain data that is violative of normal rules for only the most distinguishing features of the domain while not bothering to identify the records in which all of the provided data is directed only to less distinguishing features or non-distinguishing features.

After the anomaly-containing records have been identified in step 220, Big Data processing techniques are used in step 230 to determine where along each single-variate feature dimension there are concentrated clusters of anomalies and where along each such single-variate feature axis (e.g., axis 173 of plot 170 in FIG. 1B) there are no, or less then a predetermined threshold number of anomalies. By way of example, if the horizontal plotting-along axis represents IP addresses (places 173) and the vertical measurement representing axis (e.g., 171 or 157) represents number of service requests made per unit time (e.g., per second) then the one or more IP addresses for which many instances of anomalous requests per unit time are reported may be deemed as suspicious places of possible denial of service (DOS) attacks. On the other hand, if the concentration of anomalies along the horizontal plotting-along axis is substantially uniform and there is no clustering of anomalies over any one specific, distinguishable region of the plotting along axis, then it may be determined that for the instant case, the tested feature (e.g., IP addresses) is not providing any information of distinguishable quality.

A specific example of a Big Data processing technique that may be used in step 230 for determining single-variate variance is the Kernel Density Estimation method (KDE). As well known in the statistical analysis arts, KDE is useful for determining how different any one plot point (e.g., xi) is from all other plot points in a finite set of plot points. An example of KDE analysis would be that of determining the sum of (F(xj)-F(xi))² for two or more values of i, while the other parameter j takes on all values within the set other than i. Then the sum of the square differences for a first value of i, versus that for a second value of i will indicate which plot point (xi, for i=a or b) is more different than all the rest of the plot points within the finite set. More specifically, referring to FIG. 3A, a finite set of anomalies is depicted in bounded area 310 where each five-point star (e.g., 375) represents an occurrence of anomalous behavior relative to a location on a selected, plotting-along axis 311. In the illustrated case of FIG. 3A, the vertical axis 312 indicates a percentage of deviation from a predefined normal amount (Norm1) for a measured metric such as, for example, number of requests per unit time. A KDE-based analysis might determine how many instances of anomaly are stacked up above each plot point along the X axis (311). Alternatively, and not as the only possible other option, a KDE-based analysis might determine what the maximum amount of deviation (e.g., percentage of deviation from Norm1) is present over each plot point. In the case of FIG. 3A, the results show a substantially uniform distribution. On the other hand, in the case of FIG. 3B it is seen that a KDE-based analysis might recognize at least three distinct areas under bounding box 320 and along plotting axis 321, namely, 321 a, 321 b and 321 c. Since the results of FIG. 3B include distinct clustering of anomalies over different regions of the plotting to access 321 while the results of FIG. 3A do not, it may be automatically determined that the plotting-along axis Xm2 (also 321) represents a more distinguishing feature than does the plotting-along axis Xml (also 311) of FIG. 3A for the given domain and/or context. By way of example, while the portion of axis 311 under box 310 represents IP addresses in the range 100.x.x.x to 160.x.x.x; the portions of axis 321 under box 320 may differently represent IP addresses in the range 200.x.x.x to 260.x.x.x and where distinguishable behaviors of an anomalous kind can be found in the latter range but not in the first one. Alternatively, axis 321 may represent geographic locations (e.g., postal ZIP Codes) as opposed to IP addresses.

Referring to step 235 of FIG. 2A, the analysis performed in step 230 may be used to determine where along a given feature axis (e.g., along the range of all IP addresses) distinct clustering's of anomalies occur or which feature dimensions (e.g., postal ZIP Codes as opposed to IP addresses) indicate greater distinctions for a given anomaly measurement and thus likely provide more unique information than other feature dimensions (e.g., timestamps).

In step 237, the results of step 235 are compared against feature identifying rules (section 253) in the knowledge database to thereby determine if updating of the knowledge base rules is warranted for the current domain and context. If yes, the rules are updated and control is returned to step 220 for repeat using the even more distinguishing feature axes (or subportions of feature axes) as discovered in step 235.

Thus far the discussion has focused on anomalies detected along only a single feature axis such as one, and only one of a nonlimiting set including: IP addresses, postal ZIP Codes, number of service requests per unit time and HTTP codes used in the service requests. However it is possible to map each of one or more anomaly-including log records simultaneously to two or more feature identifying axes, for example such that each identified anomaly has a same IP address and a same postal ZIP Code because, as one possible causation, the underlying client machine that is the rules-violator has a fixed IP address and a fixed postal ZIP Code.

Referring to FIG. 4A, shown is a multidimensional configuration 401 where a first plot-along axis 411 has points representing a first driven metric, Xml and an orthogonal second plot-along axis 414 has points representing a second driven metric, Xm2. Examples could include feature pairs such as: (a) Xm1=IP addresses and Xm2=Server response codes; (b) Xm1=Postal Zip Codes and Xm2=Cellular Telephone Service providers (e.g., Verizon™, Sprint™, etc.); (c) Xm1=Client generated request codes and Xm2=Server Response Times.

Each 2D mapping plane may have its own vertical results axis. For example, a first 2D mapping plane may be defined by horizontal axis 411 and vertical axis 412 where the vertical axis 412 provides a first deviation measure of a first measured parameter, Mp1 (the exemplary deviation measure being illustrated as an absolute value of (Mp1-Norm1)/Norm1 where Norm1 is the rules-defined normal value for Mp1). A second 2D mapping plane may be defined by horizontal axis 411 and vertical axis 413 where the vertical axis 413 provides a second deviation measure of a second measured parameter, Mp2 (the exemplary deviation measure being illustrated as a square of (Mp2-Norm21)/Norm2 where Norm2 is the rules-defined normal value for Mp2). Anomalies that are detected only for the first 2D mapping plane (411 versus 412) are depicted as white filled five point stars 475 (see also 451 in the legend of FIG. 4D) while anomalies that are detected only for the second 2D mapping plane (411 versus 413) are depicted as hatch filled, tilted five point stars 476 (see also 452 in the legend of FIG. 4D). Anomalies that are detected simultaneously for both of the first and second 2D mapping planes and are displayable at the same 3D point of the multidimensional configuration 401 are depicted as 3D stars like the one illustrated at 453 in the legend 404 of FIG. 4D.

In the case of such multi-dimensional configurations, clustering and/or aggregation may be carried out by simultaneously considering two or more distinguishing feature axes such as 421 and 424 depicted in FIG. 4B. A first clustering and/or aggregation result is represented by a multidimensional object 420 a. A second such result is represented by a spaced apart multidimensional object 420 b and so on. The first clustering and/or aggregation result 420 a for example, populates range 421 a along the Xml axis and range 424 a along the Xm2 axis. It also has correspondingly populated ranges along the one or more vertical axes, such as the illustrated and shared vertical axis 422 in FIG. 4B.

Referring back to FIG. 2A, in optional step 240 determinations are automatically made at least for two distinguishing features (e.g., corresponding to axes 421 and 422 of FIG. 4B) as to what compound feature variances may exist in such multi-dimensional spaces (e.g., corresponding to 410 of FIG. 4A) for example by using multi variate KDE analysis. An example of a multivariate KDE analysis would be that of determining the square root of two sums such as the square root of F(xj)-F(xi))² plus (G(yk)-G(yi))² four all values of j and k other than i so as to thereby determine a multidimensional effective distance between one or more anomalies detected above coordinate point xi, yi on an underlying 2D plot-along plane. The xi, yi coordinate points having the greatest effective spacing apart distance are then deemed as outliers within the tested boundary space (e.g., 410 of FIG. 4A) while the xi, yi coordinate points having the smallest effective spacing apart distance are deemed to be cluster centers because they have many nearby other anomalies.

In optional step 245, determination's are made of where distinct clustering's of anomalies occur within the tested multidimensional spaces based on compound feature variance analysis such as multivariate KDE analysis. Then in step 247 is determined whether the expert knowledge base rules for corresponding multivariate spaces need to be updated for the given domain and context. If the answer is yes control is returned to step 220, the rules for multivariate anomalies identification are updated and the remaining portions of step 220 through 245 are repeated. If the answer to test step 247 is no, then in subsequent step 260 and automatic identification is made of the more distinguishing ones of the compound features usable in the respective domain and context. Optionally, the identified more distinguishing ones of the compound features are ranked so as to identify the most distinguishing one of the compound features and then the second most distinguishing one and so forth.

In step 270, the single variate and multi variate feature spaces that are identified as being most distinguishing in respective steps 235 and 260 are used to generate de-duplicated business-relevant alerts with added insights by way of a combination of anomaly aggregation steps and aggregation bypassing steps.

Referring to FIG. 2B, one possible embodiment 270′ for generating de-duplicated alerts is illustrated. Entry may be made at 271 a. In step 271 b, a workload reduction process is initiated. The purpose of this workload reduction process is to identify and trim away anomalies which are clearly non-aggregable using a trimming process that is computationally less intensive than actual aggregation.

In step 272, a dimensionality value (e.g., 1D, 2D) is picked and a corresponding one or more distinguishing feature axes are picked for performing the trimming away operation. In step 273 a bounded set of anomaly-containing records are picked for the trimming operation. A 2D example of such a bounded set would be the corresponding records for the anomalies inside area 320 of FIG. 3B. Next, in step 274, KDE and/or other variance quantifying analysis is carried out on the anomaly definitions within the bounded set to thereby determine which are most likely to be cluster centers and which are most likely to be outliers spaced far apart from one or more cluster centers. For example and referring again to FIG. 3B, an anomaly point located at the center of the cluster above X axis section 321 a might be automatically determined to constitute a cluster center. On the other hand, one or more of the anomaly points in the middle of the thin spread above X axis section 321 b might be automatically determined to constitute an outlier.

Also in step 274 the identified outliers within the bounded set are trimmed away and stored into a so-called bypass pool whose anomalies will not be subjected to intensive aggregation analysis. Referring to FIG. 3C, curved arrow symbol 335 represents a sending of the anomalies in blocked regions 342 and 343 two and aggregation bypass pool. Curved arrow symbols 331 and 332 represent a discarding of anomalies outside the predetermined bounding set 320 of FIG. 3B. the result of the trimming away steps (331, 332, 335) is shown in FIG. 3D. The set of anomalies that are potentially to be subjected to a computationally intensive aggregation process has been reduced.

Next, in step 275 of FIG. 2B, respective clusterings of what remains (e.g., blocked regions 341 and 344 of FIG. 3C) are deemed to be new bounded data sets to be subjected to further selective trimming. Then in step 276 a, similar KDE and/or other variance analysis is used to automatically identify the outliers and the cluster centers of the new bounded data sets (e.g., inside blocked regions 341 and 344 of FIG. 3C). Step 276 b determines if there are more outliers to be sent to the aggregation bypass pool. If yes, control passes to step 276 c where the outliers are sent to the bypass pool and then further shrinkage is attempted in step 275. Steps 276 a through 276 c are repeated until there are no more detectable outliers.

Referring to FIG. 3D, depicted is a condition 304 where a previous bounding set 341 has been shrunken to a smaller bounding set 341″ and outliers of X axis region 321 e are to be trimmed away (336) and sent to the bypass pool. Similarly, outliers in X axis region 321 f are to be trimmed away (337) and also sent to the bypass pool. Then further KDE and/or other variance analysis is to be applied to the remaining anomalies inside the shrunken bounding sets 341″ and 344″.

At step 277 of FIG. 2B it has been determined that there are no more detectable outlying anomalies to be sent to the aggregation bypass pool. Computationally intensive aggregation rules found in the domain specific knowledge base are used to aggregate remaining ones of the anomalies into corresponding one-from-many alert reports. More specifically, but as not yet explicated, in one embodiment, various models are used from within the knowledge database to identify more likely ones of fault/failure models and the relevant distinguishing feature axes of these, to identify more likely ones of end-user models for determining what alert information the end-user of the current domain and context will likely not want to see and what alert information (if any that is left) the end-user is most likely desirous of seeing. The goal is to reduce the number of presented alerts to a bare minimum as opposed to flooding the end-user with an overwhelming barrage of meaningless (to the end user) and unactionable (for the end user) data. The function of combining co-related anomalies (those related by way of the fault/failure models and of the end-user models into a minimalized list of most relevant alerts is generally substantially more computationally demanding than that of identifying outliers in a simplified single or double features space using KDE and/or other variance analysis.

At step 278, the non-aggregable anomalies in the bypass pool are referenced and corresponding one-for-one alert reports are generated for these. Because computationally intensive aggregation has not been applied to the anomalies in the bypass pool, processing time is saved, workload on computational resources of the system are reduced and thus performance and efficiency are improved.

In step 279, the generated alerts of step 277 and of step 278 are merged for purposes of determining how their respective alerts will be presented in an alerts visualization process.

Step 280 of FIG. 2A represents the presentation of de-duplicated alerts in a business relevant manner to a visualizing dashboard (see FIG. 6) based on identified business relevant features inferred from expert knowledge base rules in the knowledge database 250. More specifically, section 253 of the utilized expert knowledge base 250 may include rules for identifying business relevant ones of the more distinguishing features (single variate and/or multivariate) which are most relevant to the specific business of the end-user. For example, if the end-user business is directed to selling large volumes of textbooks to colleges and other educational institutions, then one of the business relevant distinguishing features might be whether the name of the webpage download requester ends with a .EDU domain identifier. On the other hand, if the end-user business is redirected to selling individual but high-priced coffee table books to individuals with large disposable incomes, then one of the business relevant distinguishing features might be whether the geographic location from which the webpage download request came is identified as a high income location.

Section 253 of the knowledge database may further include rules directed to how alerts should be visualized for each given domain, context and specific end-user business. These visualization rules may determine how various pieces of insight-providing information are to be presented, including whether they should be in the form of pie charts, bar graphs, numeric plots or other appropriate forms. The visualization rules may be made adaptive to user preferences. For example, if an end-user indicates dislike for a particular format of information presentation, the ranking for using such format is reduced. Briefly, FIG. 5B includes a set of visualization options switches 533 which indicate what type of visualizations should be channeled to an alert presenting dashboard 536. A further unit 537 automatically detects user preference indications regarding recently presented dashboards and forwards positive and negative feedback to a knowledge base unit 531 which drives the visualization options switches 533. While a number of examples are provided in FIG. 2A for the various kinds of expert knowledge base rules that might be stored in the knowledge database 250, it is within the contemplation of the present disclosure to store and use yet additional kinds of rules for determining which log files of which servers are to be analyzed, which fields in the respective records of the log files are to be analyzed, which feature dimensions are to be analyzed for detection of anomalies, which normal behavior rules are to be used for identifying anomalous behavior, which information theory clustering algorithms are to be used for identifying outlier anomalies and center-of-cluster anomalies, which of the analyzed feature dimensions are to be deemed as the more distinguishing features based on domain, context and business specifics; how clustered together anomalies are to be aggregated into singular alert reports; how alert reports are to be visually presented to end-users in a business relevant manner and how rules within the knowledge database are to be adaptively modified over time and with gathering of additional experiential knowledge about the workings of the domain and the preferences of the end-user. It is to be appreciated that expert rules are but one way of operating a knowledge base and that other methods including use of neural network learning are contemplated for converting raw log file data into useful and meaningful presentation of alerts to end-users. It is to be appreciated that after end-user directed, meaningful alerts are presented (e.g., visually and/or audibly) to a corresponding end user in step 280 that the end-user may then take appropriate remedial action, for example calling in experts in the subject matter of the identified relevant/distinguishing features to further look into the problem and/or following one or more automatically supplied recommendations (see briefly, 673 of FIG. 6) provided by an alerts presentation screen.

Referring to FIG. 2C, further content of the knowledge database is shown at 250″. In order to provide good insight to a user of the alert reporting system, it is useful to identify the underlying one or more fault and cascading failure models at work when various anomalies are detected. The fault and failure models will vary depending on system structure and the various ways that faults and failures can present themselves in such a structure. Merely for sake of example it is assumed at 254 a that a system structure is vulnerable to single point denial of service (DOS) attacks and one of the consequences will be increased response time. More specifically a first fault/failure model 254 a may assume that a single program (DOS pgm) infects a single location among the client population of the system and that one program is responsible for a high number of complex service requests that are causing a detected anomaly of unusually large number of requests and longer response times. The model predicts that a same IP address will be associated with the unusually large number of requests anomaly. The model further predicts that a same geographic address will be associated with the anomaly. Moreover because a single DOS program is repeatedly outputting the same HTTP coded requests for the complex services, the same anomalies will strongly correlate with a feature axis having one or more of the HTTP codes. The same fault/failure model 254 a may further predict a set of cross-correlated failure attributes such as longer response times, congested communication links and overburdened servers.

A second and slightly different fault/failure model is depicted at 254 b. Here, the DOS attack is modeled as being sourced from many different locations but still buy a same one DOS program. Accordingly, the fault attributes differ from those of the first model 254 a for example in predicting that a set of different IP addresses of the many attack sourcing locations will be associated with the relevant anomalies, that the associated usernames could vary over the set of different geographic addresses. However, because the model assumes a same one DOS attack program, the same HTTP request codes will again be used. Also in this second model 254 b, it is assumed that the attacker will try to be less conspicuous by providing a smaller number of less complex requests per source location. Nonetheless, the failure attributes may include a much longer set of response times due to the larger number of attacking locations. The attacked servers may be more severely overburdened in the second model as compared to the first model. These are just a few simple examples and it is to be appreciated that the present disclosure contemplates a much larger set of fault/failure models that are not merely limited to DOS attacks but rather cover a substantially full gamut of different faults that the system may be susceptible to, including, but not limited to: communication subsystems faults; operating system and/or application program logic faults; hardware reliability faults due for example to changing temperatures, changing power supply conditions, mechanical vibrations and poorly made electrical contacts; and so on.

FIG. 2C additionally indicates at 254 c that the models may identify the interrelated relevant feature axes of each fault model, for example that the feature axes of IP address, geographic address and username might strongly correlate for certain types of faults. FIG. 2C additionally indicates at 254 d that the models may identify the interrelated relevant failure feature axes that correlate with one or more fault models, for example that the anomaly axis of high number of requests may strongly correlate with the anomaly axis of slowed response time and/or congested communication link; and so on.

In addition to creating, storing and using fault/failure models, the alert reporting system of the present disclosure may rely on end-user models for better understanding what kinds of alerts will be most relevant to different kinds of end-users of the reporting system. For example, at 255 a of FIG. 2C there is shown part of a model for a global system manager (User_1). This first user may have certain jobs specific goals and objectives including that of being alerted with respect to the overall health of the entire system but not being bothered with details respecting local failures. For example, the first user may desire to be alerted as to failures that affect large geographic areas but not those which affect small geographic zones. This user may wish to be alerted two significant drops in average client satisfaction over large geographic areas, where the drops are reported in terms of percentage and not in terms of absolute number details. This same user may nonetheless wish to be alerted to extreme cases of specific client dissatisfaction so that the user can delegate the task of soothing and extremely irate (and perhaps influential) customer to a subordinate.

By way of further example a second end-user of the alert reporting system is modeled at 255 b as being a local retail sales manager. Unlike the goals of the first exemplified end-user, this second end-user is interested only in the health of the local retail services providing system, not of the whole system. The geographic interests scope of this second end-user may be localized to one or a small set of geographic addresses. This second end-user may be interested in being alerted as to local client satisfaction and dissatisfaction details. This second end-user may be interested in immediately receiving alerts about extreme dissatisfaction by key customers so that the second end-user can immediately attend to soothing those customers rather than delegating the task to subordinates.

FIG. 2C further indicates at 255 c that the modeling of end-users may cover the amount of time they can spend reviewing each presented alert and the amount of delay time they will tolerate for receiving alerts of extreme urgency. Moreover, each end-user may have different preferences for the way in which alerts are presented to them, for example some may prefer pie charts while others prefer numerical tables or qualitative text for defining the alert and its significance to the associated end-user. A variety of different alert presentation rules may be created stored and used for different kinds of end-users including global level managers and local system managers with respect to how they prefer to have alerts presented to them and with respect to if and how they prefer to have recommendations and/or insights presented to them. Insights may explain one or more identified fault/failure models believed to be responsible for the observed anomalies. Recommendations may indicate system-suggested ways in which the alerted situation should be dealt with.

Use of the here-exemplified, fault/failure models and end-user servicing models can greatly increase the complexity of aggregating together anomalies that cross correlate relative to the utilized models. By trimming away of outlier anomalies from the aggregation process, the amount of work that the system needs to do and the amount of resources consumed can be reduced. Single variate trimming away of outlier anomalies has been described with respect to FIGS. 3B-3D. FIGS. 4B and 4C depict similar operations for multi-variate anomalies. Multidimensional block 420 a represents a first bounded set of anomalies that have been identified as clustering together through use of KDE and/or other information variance analysis. Similarly, multidimensional blocks 420 b, 420 c and 420 d represent further bounded sets of anomalies that also have been identified as respectively clustering together. Curved arrow symbol 435 indicates that outlier anomalies present outside of the multidimensional blocks 420 a-420 d have been dispatched to an aggregation bypass pool. Then, in a subsequent state 403 represented in FIG. 4C, further multivariate KDE and/or other information variance analysis identifies outliers within initial multidimensional blocks 420 a-420 d and shrinks the blocks to form the illustrated next bounded sets 420 e-420 h. Curved arrow symbol 436 indicates that outlier anomalies present outside of the multidimensional blocks 420 e-420 h have been dispatched to an aggregation bypass pool. When a data reduction state is reached where there are no further, clear outliers to dispatch to the bypass pool, the more computationally intensive aggregation processes are carried out on the remaining multidimensional blocks (e.g., 420 e-420 h) so as to thereby convert groups of many anomalies respectively into single alerts. End-users are thereby relieved of the tedious task of looking through large number of anomaly reports only to discover that they are providing substantially same information about a common fault or failure.

FIG. 5A depicts more clearly how multivariate spacing can be determined as between same types of anomalies. Basically, a multidimensional distance function is used to determine how clustered together or spaced apart each of a same type of anomaly is from others of the same type. In one embodiment, multivariate anomalies are typed as either belonging to all of the utilized feature axes (e.g., 511-514) or to subsets of the utilized feature axes. The legend of FIG. 5C indicates various ways in which single variate or compounded multi-variate anomalies may be plotted over respective single plot-along dimension axes (e.g., 511) or over respective two dimensional plot along planes (e.g., the plane formed by orthogonal axes 511 and 514) or plodded through respective spaces of greater dimensionalities (not shown).

Referring to FIG. 5B, a first section 502 of an automated machine system is illustrated as comprising one or more multivariate log files (525) each having selectable event features (e.g., Feat1-FeatN). The first section 502 further comprises an intelligently operated switching section 523 for selectively picking a domain appropriate subset of the selectable event features (e.g., Feat1-FeatN) and forwarding these to an automated, multivariate anomaly detection unit 526. An output of the anomaly detection unit 526 is supplied to a further automated unit 527 that is configured to detect degrees of distinction between anomalies based on the selected subset of event features (selected by 523). An example of degree of distinction between detected anomalies is that provided by clustering analysis through multivariate KDE and/or other variance analysis.

The results of the distinction detection unit 527 are used for modifying one or more adaptive sets of expert rules. One of the adaptively modifiable rule sets 521 is used for driving (522) the feature selection switches 523 so as to pick out the most or the more distinguishing of the possible feature combinations. The degree of distinction information provided by unit 527 can be used to rank different combinations (permutations) of compound features for discovering which, in a given domain and context, provide useful information about how various anomalies correlate with corresponding sections on the tested feature dimensions. Another of the adaptively modifiable rule sets 528 is used for defining the normalcy rules used by anomaly detection unit 526 to determine what constitutes a normalcy violating anomaly and what does not. Normalcy violation may be detected with respect to one or more feature dimensions. The degree of distinction information provided by unit 527 can be used to rank different combinations (permutations) of features for discovering which, in a given domain and context, provide useful information about how various anomalies should be detected or ignored.

FIG. 5B also illustrates an alert presentation section 503 which receives (524) anomaly detection reports and other information from the first section 502. The alert presentation section 503 includes a visualization options unit 535 that pre-generates different visualizations for detected anomalies or aggregations thereof. An intelligent visualization selecting unit 531 drives (532) a set of switches 533 which determine which of the pre-generated visualizations should be forwarded to a user-viewable dashboard display 536. User preference feedback that is collected by unit 537 may be supplied to the adaptive expert rules of unit 531 for modifying how various alerts and associated insight information are to be presented to the user in accordance with the end-user's likes and dislikes.

Referring to FIG. 6, illustrated is an example 600 of an alerts presenting dashboard that may be presented to an end-user by way of an appropriate computer output display monitor. Each displayed alert, such as 610 and 650 may be the result of aggregation of tens or hundreds of individual anomaly detections (e.g., 645 a-645 n and . . . —685 n). However the detailed information of these individual anomaly detections is hidden from the end-user unless the end-user activates a details magnification tool, 645 and/or 655. Instead, the respective alert reports (e.g., 610, 650) expand in the left to right direction to a series of blocks (e.g., 612, 620) that respectively have associated with them identifications of what the machine system determined to be most relevant features within recently collected log files, medium relevant features (block 620) and least relevant features (indicated by ellipses 640).

In the illustrated example, a pulldown menu 615 can be unfurled from block 612 to reveal in ranked order, the features that the reporting system determined to be the most relevant ones. More specifically for the illustrated example, the feature ranked as the most important of all is shown at 612 a to be that of anomalies having a same originating IP address. A user operable magnification tool 613 a allows the user to see further details regarding this identified as most relevant feature in a details revealing block such as 614 a. Further in the illustrated example, the feature ranked as next most important is shown at 612 b to be that of anomalies having an excessively slow response time. If magnified, the details 614 b for this feature may indicate that the excessively slow response times are those greater than 250 milliseconds. Yet further in the illustrated example, the feature ranked as third most important at 612 c is that of the same username being predominantly associated with the aggregated anomalies (645 a-645 n), where in the example the chosen user handle is “Dirty Harry” as indicated in the popped out details bubble 614 c. Drop-down menu 615 may contain additional features deemed as relevant. In one embodiment, the amount of drop-down of the menu 615 determines how many of the top N features will be revealed.

In one embodiment, a secondary expansion of each alert block (e.g., 610) reveals so-called “insight” information about the reported alert. More specifically in the example of alert 610, a first insight 630 indicates that it is probably a hacker initiated denial of service (DOS) attack. The dashboard user may request additional information by activating a magnification tool 631 a. In the example, this causes display of a diagnostic details bubble 632. One of the diagnostic details might be the fact that the named service requestor, “Dirty Harry” is already known to be a persistent hacker due to knowledge accumulated in the knowledge database (250). Other backup pieces of information that might be provided in the diagnostic details bubble 632 (but are not shown for sake of illustrative simplicity) are the facts that the anomaly related service requests all came from a same IP address of origin (“Dirty Harry's” home computer), they all resulted in an excessively slow response time (as indicated at 612 b) and they all used a same sequence of HTTP request codes (not shown).

The exemplary details for the illustrated second alert 650 are basically the same except that the insight box 670 indicates the anomalies to be related to an over-fragmented magnetic hard disk. In one embodiment, the insight bubble 670 may expand down and out to reveal a recommended actions bubble 673 where, in the instant case, the recommendation might be to defragment the associated hard disk.

FIG. 1A illustrated a small portion of an enterprise wide system. Next referring to FIG. 7, a more detailed description is provided for an enterprise system 700 having anomaly detecting and reporting portions installed for at least some and preferably substantially all of the request servicing parts (e.g., 131′-13 n′) of the system.

More specifically, the illustrated integrated client-server/internet/cloud system 700 (or more generically, an integrated multi-device system 700) in which the here disclosed technology is applied may also be referred to as an SaaS serviced, distributed resources, machine system in which there are provided a variety of differently-located data processing and data communication mechanisms including for example, customer-sited units (e.g., wireless smartphone 110′) configured to allow end-users thereof (e.g., U1) to request from respective end-user occupied locations (e.g., LocU1) services from differently located enterprise hosts (e.g., in-cloud servers 131′, 132′, . . . 13 n′ having respective siting locations LocX1, LocX2, LocXn). There is further provided an enterprise resources monitoring and managing center (SaaS 740) tasked with the job of monitoring all mission-vital points within the system 700 and with the job of managing corresponding hardware and software portions so that pre-specified business reliability, security customer servicing goals of ‘cliental’ of the SaaS can be realized.

It is to be understood that the illustrated system 700 is merely exemplary. As indicated, it comprises at least a few, but more typically a very large number (e.g., thousands) of end-user devices 110′ (only a few shown in the form of wireless smartphones but understood to represent many similarly situated mobile and/or stationary client machines including the smartphone wireless client kinds and cable-connected desktop kinds). These end-user devices 110′ are capable of originating service requests which are ultimately forwarded to service-providing host machines (e.g., in-cloud servers 131′, 132′, . . . 13 n′) within a cloud environment. Results from the service-providing host machines are thereafter typically returned to the end-user devices 110′ and displayed or otherwise communicated to the end-users (e.g., U1, U2, Un). Total response time to client requests typically includes a sum of response times by various task servicing servers to delegated subtasks of the request. A denial of service attack originating from locations of one or more users (e.g., U2, U3) may include generating an unusually large number of service requests whose implementation is relatively complex and greatly tasks targeted computational resources (and/or communication resources) of the system. For example, if a business goal of a retail portion 760 of the enterprise is that of online selling of rare hard covered art books, the end-user (U1) may have installed on his/her smartphone (110′) a software application (“app”) that automatically requests from the enterprise, a list of such books that may be of current interest to the end-user (U1). In response to the request, enterprise software and hardware modules automatically identify the user, pull up a user profile (e.g., including user password and financial details), search for matching books, and then within a very short time (e.g., a minute or less), communicate back the list for almost instant playout on the end-user's device 110′. Since in this example, the search is for relatively rare books, specialized databases may have to be queried. This may utilize a greater part of system resources than a more typical search for popular and readily available books. Upon receiving the list of available rare books the requesting client user may then click on one of the offered selections and ask to instantly purchase the book while having his online account charged. This may entail transactions more complex than a normal book purchase because legal rights to one of a rare few of such books may need to be secured. Thus the system is stressed more than by a normal amount. A hacker may gain knowledge of this phenomenon and try to exploit it for carrying out a DOS attack.

The client user device 110′ may be a mobile device which dynamically connects with the network by way of anonymous Wi-Fi™ or cellular connection points (AP's). In accordance with the present disclosure, event reporting data streams 731′ through 73 n′ are generated by the various servers tasked with handling the requests or delegated subtasks of these requests (e.g., by way of server log file and event reporting generators such as indicated at 13 n.2 in FIG. 7). Remote accessibility to such generated event reporting data streams may be provided by remote SaaS access means such as indicated at 750. The access reports may be streamed into and captured by one or more event monitoring units such as the illustrated events tracker 751 and events database 752. Correspondingly appropriate, anomaly detecting programs and/or firmware watchdogs (not explicitly shown) are provided at the SaaS Center 740 and/or otherwise distributed about the system for detecting various types of anomalies on an urgent or less than urgent basis depending on predetermined prioritization schemes (e.g., stored in the knowledge database 250′). The detected anomalies are then processed in accordance with various aspects of the present disclosure, including that of aggregating closely co-related anomalies so that only a single alert report is generated for all the closely co-related anomalies while individualized further alert reports are generated for outlier anomalies.

Aside from the end-user devices (e.g., 110′) and the cloud servers (e.g., 131′, 132′, . . . , 13 n′) the system 700 comprises: one or more wired and/or wireless communication fabrics 115′ (only one shown in the form of a wireless bidirectional interconnect) coupling the client(s) 110′ to networked servers 120′ (not explicitly shown, and can be part of an Intranet or the Internet) where the latter may operatively couple by way of further wired and/or wireless communication fabrics 125′ to further networked servers 130′ (e.g., 131′, 132′, . . . 13 n′).

The second set of networked servers 130 is depicted as a “cloud” 130′ for the purpose of indicating a nebulous and constantly shifting, evolving set of hardware, firmware and software resources. In-the-cloud resources are typically used by large scale enterprise operations for the purpose of keeping mission critical tasks going without undue interruptions. As those skilled in the art of cloud computing appreciate, the “cloud” 130′ may be implemented as reconfigurable virtual servers and virtual software modules implemented across a relatively seamless web of physical servers, storage units (including flash BIOS units and optical and/or magnetic storage units), communication units and the like such that point failure of specific units within the physical layer are overcome by shifting the supported virtual resources to spare other support areas in the physical layer. Because of sheer size and also the constantly shifting and self-reconfiguring fabric of resources, it can be very difficult to monitor and manage all the hardware and software resources of the system 700. The latter task is often delegated to an SaaS services provider (e.g., 740). Although data processing and communication resources can be virtualized in the cloud, it nonetheless has a physically real support layer composed of servers, routers, switches and so forth that typically have event reporting and logging means such as 13 n.2 incorporated in them. As illustrated in FIG. 7, one or more of the event reporting streams (e.g., 731′ -73 n′) are forwarded at least to the SaaS services providing center 740 and/or to other sites (e.g., local manager site 760) for automated monitoring, automated detecting of relevant anomalies and automated generating of appropriate alert reports to various different kinds of end-users (e.g., global user 755 and local user 765) of the anomaly detecting and alert generating system.

Still referring to FIG. 7, a further walk through the illustrated system 700 is provided here so that readers may appreciate the bird's eye lay of the land, so to speak. Item 111′ represents a first user-activateable software application (first mobile app) that may be launched from within the exemplary mobile client 110′ (e.g., a smartphone, but could instead be a tablet, a laptop, a wearable computing device; i.e. smartwatch or other). Item 112′ represents a second such user-activateable software application (second mobile app) and generally there are many more. Each client installed application (e.g., 111′, 112′) can come in the form of nontransiently recorded digital code (i.e. object code or source code) that is defined and stored in a memory for instructing a target class of data processing units to perform in accordance with end-user-side defined application programs (‘mobile apps’ for short) as well as to cooperate with server side applications implemented on the other side of communications links 115′ and/or 125′. Each app (e.g., 111′, 112′) may come from a different business or other enterprise (e.g., book selling business) and may require the assistance of various and different online resources (e.g., Internet, Intranet and/or cloud computing resources). Generally, each local level enterprise portion (e.g., 760) is responsible for maintaining in good operating order its portions of the (e.g., Internet, Intranet and/or cloud computing resources). Each business enterprise may hire or otherwise employ a SaaS provider 740 to manage all of its online resources. Plural business or other enterprises can pool parts of their resources into a common core of resources that are watched over by a single SaaS provider 740 so as to reduce operating costs.

In one embodiment, one or more of the mobile apps are instrumented so that in the background they provide useful quality control data that can be picked up by the SaaS provider 740 for monitoring performance, where pickup of the quality control data may occur at different locations (e.g., LocX1, LocX2, LocXn) throughout the enterprise system 700. An example of an instrumented or ‘scoped app’ is depicted at 713. It includes an API interface 714 to the local operating system (e.g., Apple iOS™ or Android™). It may include further API's 716 to other local apps. It may further include instrumented execution code 717 where the instrumented part causes various pieces of meta-data to be embedded in the back and forth communication packets of the device 110′. Examples of such embedded meta-data may include indications of time of service-request, complexity/size of service-request, location where service-request was launched from, type of local OS, ID of cellular carrier and so forth. This embedded meta-data is picked up by backend enterprise servers and by monitoring agents thereof (e.g., embedded in servers such as 13 n′ but not explicitly shown). The picked up meta-data is used for determining system performance (for example, how long did it take from time of end-user request to complete the requested service?). In more detail, some of the embedded meta-data may be targeted for use by a SaaS backend servers such as indicated at 744 a/744 b. In accordance with one aspect of the present disclosure, the SaaS backend servers 744 a/744 b may monitor for local and global violations of normalcy rules as detected by the anomaly detecting units/services (e.g., 751) distributed throughout the system. The local and global anomaly defining lists and/or rules may be locally stored in the respective anomaly watchdog units and/or in the central SaaS knowledge database 250′.

Typically, large systems such as 700 are subdivided into management-defined “sections”. The size and resources inventory of each section is left to mangers of the system, but generally each section; where 740 is used here as an example of a system section, includes a limited number of intercoupled, “local” resources such as one or more local data processing units (e.g., CPU's 741), one or more local data storage units (e.g., RAM's 742, ROM's 743, Disks 746), one or more local data communication units (e.g., COMM units 3747), and a local backbone (e.g., local bus 745) that operatively couples them together as well as optionally coupling them to yet further ones of local resources 748. The other local resources 748 may include, but are not limited to, specialized high speed graphics processing units (GPU's, not shown), specialized high speed digital signal processing units (DSPU's, not shown), custom programmable logic units (e.g., FPGA's, not shown), analog-to-digital interface units (A/D/A units, not shown), parallel data processing units (e.g., SIMD's, MIMD's, not shown), local user interface terminals (e.g., 754) and so on.

It is to be understood that various ones of the merely exemplary and illustrated, “local” resource units (e.g., 741-748) may include or may be differentiated into more refined kinds. For example, the local CPU's (only one shown as 741) may include single core, multicore and integrated-with-GPU kinds. The local storage units (e.g., 742, 743, 746) may include high speed SRAM, DRAM kinds as well as configured for reprogrammable, nonvolatile solid state data storage (SSD) and/or magnetic and/or other phase change kinds. The urgency of dealing with unusual behaviors (e.g., anomalies) in these various kinds of data processing and data storing resources may vary depending on their frequency of use and criticality to enterprise missions. For example a single outlier anomaly in a rarely used backup storage unit may not require immediate resolution while a single outlier anomaly in a heavily used resource may require urgent attention. As indicated above, not every end-user (e.g., 754, 764) is interested in receiving alerts direct and to such single outlier anomalies. In one embodiment the knowledge database 250′ includes expert rules (e.g., in the form of IF-THEN-ELSE expressions) for categorizing the different kinds of detected anomalies and determining if and when alert reports for these should be communicated to one or more end-users (e.g., 754, 764).

The local communication-implementing units (only one shown as 747) may operatively couple to various external data communicating links such as serial, parallel, optical, wired or wireless kinds typically operating in accordance with various ones of predetermined communication protocols (e.g., internet transfer protocols, TCP/IP). Similarly, the other local resources (only one shown as 748) may operatively couple to various external electromagnetic or other linkages 748 a and typically operate in accordance with various ones of predetermined operating protocols. Additionally, various kinds of local software and/or firmware (including that of anomaly-detecting watchdog units/services mentioned herein and of the normalcy violation monitoring portions described herein) may be operatively installed in one or more of the local storage units (e.g., 742, 743, 746) for execution by the local data processing units (e.g., 741) and for operative interaction with one another. The various kinds of local software and/or firmware may include different operating systems (OS's), various security features (e.g., firewalls), different networking programs (e.g., web browsers), different application programs (e.g., word processing, emailing, spreadsheet, databases, etc.) and so on. A further example of such locally installed software and/or firmware units is shown in the magnification for cloud server 13 n′, where that server 13 n′ includes a respective server OS 13 n.1 operatively installed therein and respective server security fences (e.g., firewalls) operatively installed therein. The locally installed software and/or firmware units my further include the server events data-streams and log file generator 13 n.2 which produces event logs and data streams including those which indicate anomalous behavior.

As mentioned, in addition to, or in place of the interactions tracker 751, the SaaS center 740 may include the events database 752 which contains organized records of various events and activities within the system for use in real time situational analysis (including real time event-monitoring, real-time anomaly detection, real time alert reporting) and or in off-line post-situation analysis. Various heuristically or otherwise developed expert knowledge rules may be stored in an expert knowledge base 250′ of the SaaS center 740 and used for analyzing and/or developing normalcy violation detecting rules and resolving rules including those to be used by the anomaly aggregating and alert generating subsystems of the system 700. The stored rules may further include those for categorizing various types of violations including those intercepted by the anomaly watchdog units/services. The stored rules may further include those for reporting and resolving various issues including those related to administrative permission violations intercepted by the anomaly watchdog units/services of the system 700. It is to be understood that the illustrated human analyzers 755, 765 can be replaced by respective automated analyzers which rely for example on the expert rules knowledge database 250′ for among other things, accessing over-time developed rules (e.g., heuristically developed rules) for resolving different issues within the monitored system 700.

As may be appreciated by those skilled in the art in light of the foregoing, aspects of the present disclosure may be deemed to be defined in any of a number of patentable classes including that of any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Aspects of the present disclosure may be implemented entirely hardware or at least partially in software (including firmware, resident software, micro-code, etc.) or by combining software and hardware implementation that may all generally be referred to herein as a “circuit,” “module,” “component,” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable media having computer readable and executable program code embodied thereon.

Any combination of one or more computer readable media may be utilized. A computer readable storage medium may be, for example, but not limited to, in the form of an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an appropriate optical fiber with a repeater, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. A signal transmission medium per se is not a computer readable storage medium.

Computer program code which programs a processor for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, CII, VB.NET, Python or the like, conventional procedural programming languages, such as the “c” programming language, Visual Basic, Fortran 2003, Perl, COBOL 2002, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) or in a cloud computing environment or offered as a service such as a Software as a Service (SaaS).

Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatuses (systems) and computer program products according to various embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams described above, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable instruction execution apparatus, create a mechanism for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that when executed can direct a computer, processor, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions when stored in the computer readable medium produce an article of manufacture including instructions which when executed, cause a computer to implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable instruction execution apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatuses or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various aspects of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular aspects only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

For purposes of this document, it should be noted that the dimensions of the various features depicted in the figures may not necessarily be drawn to scale.

For purposes of this document, reference in the specification to “an embodiment,” “one embodiment,” “some embodiments,” or “another embodiment” may be used to describe different embodiments or the same embodiment.

For purposes of this document, a connection may be a direct connection or an indirect connection (e.g., via one or more others parts). In some cases, when an element is referred to as being connected or coupled to another element, the element may be directly connected to the other element or indirectly connected to the other element via intervening elements. When an element is referred to as being directly connected to another element, then there are no intervening elements between the element and the other element. Two devices are “in communication” if they are directly or indirectly connected so that they can communicate electronic signals between them.

For purposes of this document, the term “based on” may be read as “based at least in part on.”

For purposes of this document, without additional context, use of numerical terms such as a “first” object, a “second” object, and a “third” object may not imply an ordering of objects, but may instead be used for identification purposes to identify different objects.

For purposes of this document, the term “set” of objects may refer to a “set” of one or more of the objects.

The corresponding structures, materials, acts, and equivalents of any means or step plus function elements in the claims below are intended to include any disclosed structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art in light of the foregoing but without departing from the scope and spirit of the disclosure. The aspects of the disclosure herein were chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure with various modifications as are suited to the particular use contemplated. 

What is claimed is:
 1. A machine-implemented method comprising: automatically identifying a finite set of detected anomalies within an anomalies distribution space having one or more feature-representing dimensional axes; automatically aggregating together two or more of the detected anomalies for forming a corresponding anomalies reporting alert corresponding to the aggregated two or more of the detected anomalies; before aggregating together said two or more of the detected anomalies, automatically identifying by way of a computationally less intensive variance analysis, outlier anomalies within the finite set that are least clustered together with others of the anomalies in the finite set; not performing aggregation on the identified outlier anomalies; and automatically forming corresponding anomaly reporting alerts for respective ones of the identified outlier anomalies.
 2. The method of claim 1, wherein the automatic identifying of the outlier anomalies includes using a Kernel Density Estimation (KDE) analysis.
 3. The method of claim 2, wherein the anomalies distribution space has at least two feature representing axes relative to which the detected anomalies are distributed; and said KDE analysis includes a multi-variate KDE analysis.
 4. The method of claim 1, wherein: the detected anomalies are those relating to enterprise system performance where the enterprise system includes one or more servers configured to respond to service requests originated from client machines and to provide corresponding responses to the client machines; and at least one of the feature-representing dimensional axes represents locations of request origin within the enterprise system.
 5. The method of claim 4, wherein the represented locations of request origin include Internet protocol addresses (IP addresses).
 6. The method of claim 4, wherein the represented locations of request origin include identifications of geographic locations.
 7. The method of claim 4, wherein at least one other of the feature-representing dimensional axes represents time of event.
 8. The method of claim 4, wherein at least one other of the feature-representing dimensional axes represents number of requests made per a predetermined unit of time.
 9. The method of claim 1, wherein: the detected anomalies are those relating to enterprise system performance where the enterprise system includes one or more servers configured to respond to service requests originated from client machines and to provide corresponding responses to the client machines; and at anomalies distribution space includes one or more measured performance metrics axes that are orthogonal to the one or more feature-representing dimensional axes and at least one of the measured performance metrics axes represents a response time aspect of the enterprise system.
 10. The method of claim 1 and further comprising: using pre-determined rules of violation of normal behavior stored in a knowledge database to detect said detected anomalies.
 11. The method of claim 1 and further comprising: using pre-determined domain-specific rules stored in a knowledge database to identify said one or more feature-representing dimensional axes.
 12. The method of claim 1, wherein: the detected anomalies are those relating to enterprise system performance where the enterprise system includes one or more servers configured to respond to service requests originated from requesting other machines and to provide corresponding responses to the requesting other machines; the one or more servers are configured to produce a corresponding event log files; the method further comprises using predetermined log file mapping rules to map information of at least one event log file to corresponding plot sections distributed along at least one of the feature-representing dimensional axes.
 13. An automated machine system comprising: a knowledge database storing expert rules including rules for aggregating together identified pluralities of identified anomalies for forming from the aggregated anomalies a corresponding one anomaly alert report; an anomalies pre-processing unit configured to identify cluster-centered ones and outlier ones of a finite set of anomalies before aggregation of a subset of the finite set of anomalies is performed; and an anomalies aggregating unit configured to aggregate anomalies within the finite set of anomalies which are not pre-identified as outlier anomalies; and a report generating unit configured to generate alert reports including at least one alert report corresponding to an aggregated plurality of anomalies and at least a second alert report corresponding to an identified outlier anomaly.
 14. The machine system of claim 13, wherein: the anomalies pre-processing unit is configured to automatically identify outlier anomalies by using at least a Kernel Density Estimation (KDE) analytical algorithm.
 15. The machine system of claim 14, wherein: the identified anomalies include those relating to enterprise system performance of an enterprise system that includes one or more servers configured to respond to service requests originated from client machines and to provide corresponding responses to the client machines; and the anomalies pre-processing unit is configured to use at least one of a plurality of the feature-representing dimensional axes to determine which of the anomalies are clustered together and which are outliers.
 16. The machine system of claim 15, wherein: at least a used first one of the plurality of the feature-representing dimensional axes represents locations of request origination.
 17. The machine system of claim 15, wherein: at least a used first one of the plurality of the feature-representing dimensional axes represents number of requests made per a predetermined unit of time.
 18. The machine system of claim 15, wherein: at least a used first one of the plurality of the feature-representing dimensional axes represents a response time aspect of serviced requests.
 19. A computer program product comprising: a computer readable storage medium having computer readable program code embodied thereon for programming a processor, the computer readable program code comprising: computer readable program code configured to identify anomalies within streamed event data such as captured in a server log; computer readable program code configured to analyze the identified anomalies as distributed within an anomalies distribution space having one or more anomaly distinguishing feature dimensions and to separate apart outlier anomalies from clusters of other anomalies, the separated apart outlier anomalies being stored in an aggregation bypass pool; and computer readable program code configured to use knowledge base aggregation rules to aggregate together those anomalies which have not been separated apart as outlier anomalies while not aggregating the outlier anomalies.
 20. A computer program product of claim 19 and further comprising: computer readable program code configured to generate alert reports including one from many reports generated for the aggregated together anomalies and one for one reports generated for the outlier anomalies. 